Injecting contextual entity variables into action payloads

You can inject contextual workflow entities via variables into the remote action payload template.

On this page:

1 Entity Variables
- 1.1 Syntax
  - 1.1.1 Shorthand notation
  - 1.1.2 Formal notation
- 1.2 Entities
2 Actions
3 How-to Articles
4 Frequently Asked Questions (FAQ)

Entity Variables

You can inject contextual variables with workflow entities into the remote action payload templates.

Syntax

There are two different syntactical notations to refer to variables:

Shorthand notation

The shorthand notation is $entity.key / $entity.key.subkey – using this shorter notation is usually preferable for brevity, and also required within the Automate with AWS post function and Automate with AWS workflow condition.

Formal notation

The formal notation is ${entity.key} / ${entity.key.subkey} – using this longer notation is optional in general, but not supported within the Automate with AWS post function and Automate with AWS workflow condition.

Entities

The currently available entities are:

Actions

You can inject contextual variables into the following actions:

Page:

Using the Automate with AWS notification recipient in Bamboo — Use the Automate with AWS notification recipient to run remote actions with AWS from Bamboo notifications, specifically from plan level and system level notifications.
Page:

Using the Automate with AWS post function in Jira — Use the Automate with AWS post function to run remote actions with AWS from Jira workflow post functions.
Page:

Using the Automate with AWS task in Bamboo — Use the Automate with AWS task to run remote actions with AWS from Bamboo jobs, specifically from builds and deployments.
Page:

Using the Automate with AWS then action in Jira Service Management — Use the Automate with AWS then action to run remote actions with AWS from Jira Service Management automation rules.
Page:

Using the Get Systems Manager Parameter action — Use the Get Systems Manager Parameter action to evaluate remote conditions so that you can control Jira Service Management automation rules via the Automate with AWS if condition, control Jira workflow transitions via the Automate with AWS workflow condition and Automate with AWS workflow validator, and fail or succeed Bamboo builds and deployments via the Automate with AWS task. You can also use this action to inject remote configuration data and secrets stored as secure parameters in the AWS Systems Manager Parameter Store, or stored as secrets within AWS Secrets Manager.
Page:

Using the Invoke Lambda Function action — Use the Invoke Lambda Function action to process Bamboo tasks and notifications, Jira workflow transitions and Jira Service Management automation rule executions with AWS Lambda, which lets you run code without provisioning or managing servers:
Page:

Using the Publish SNS Message action — Use the Publish SNS Message action to relay Bamboo tasks and notifications, Jira workflow transitions and Jira Service Management automation rule executions via the Amazon Simple Notification Service (SNS), a fast, flexible, fully managed push notification service that lets you send individual messages or to fan-out messages to large numbers of recipients:
Page:

Using the Put EventBridge/CloudWatch Events action — Use the Put EventBridge/CloudWatch Events action to process Jira workflow transitions, Jira Service Management automation rule executions, and Bamboo tasks and notifications with Amazon EventBridge (Amazon CloudWatch Events) to connect application data from your own apps, SaaS, and AWS services:
Page:

Using the Put Systems Manager Parameter action — Use the Put Systems Manager Parameter action to persist event data from Bamboo tasks and notifications, Jira workflow transitions and Jira Service Management automation rule executions into the AWS Systems Manager Parameter Store that you can then consume in subsequent automation workflows. This allows you to decouple the capturing of secrets and configuration data from Jira Service Management request approvals, Jira issue edits or Bamboo plan executions from the decision to trigger subsequent automation by one or more target services:
Page:

Using the Send SQS Message action — Use the Send SQS Message action to relay Bamboo tasks and notifications, Jira workflow transitions and Jira Service Management automation rule executions via the Amazon Simple Queue (SQS), a fully managed message queuing service that enables you to decouple and scale microservices, distributed systems, and serverless applications:
Page:

Using the Start Step Functions Execution action — Use the Start Step Functions Execution action to process Bamboo tasks and notifications, Jira workflow transitions and Jira Service Management automation rule executions with AWS Step Functions to coordinate multiple AWS services into serverless workflows so you can build and update apps quickly:
Page:

Using the Start Systems Manager Automation Execution action — Use the Start Systems Manager Automation Execution action from Bamboo tasks and notifications, Jira workflow transitions and Jira Service Management automation rule executions to simplify common maintenance and deployment tasks of Amazon EC2 instances and other AWS resources via AWS Systems Manager Automation. Automation enables you to do the following.:

How-to Articles

Page:
Editing a plan notification does not seem to take affect

Frequently Asked Questions (FAQ)